Verification method and apparatus for user signing fast payment with bank card

ABSTRACT

A user verification method may comprise: by an application, performing an account verification on account information of a to-be-verified user; performing, based on a stored mobile phone number in the account information, a mobile phone number verification on a user terminal in which the application is located if the account verification succeeds; sending an identification code of the application and the stored mobile phone number to a back-end server of the application if the mobile phone number verification succeeds, and sending a verification request packet generated according to the identification code and basic information of the stored mobile phone number to a target base station; receiving the verification notification returned by the back-end server, and determining, according to the verification notification, whether the verification of the to-be-verified user succeeds; and performing a fast payment signing process to generate a fast payment agreement when the verification of the to-be-verified user succeeds.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of International Patent ApplicationNo. PCT/CN2020/071161, filed on Jan. 9, 2020, which is based on andclaims priority to and benefit of Chinese Patent Application No.201910283959.3, filed with China National Intellectual PropertyAdministration (CNIPA) of People's Republic of China on Apr. 10, 2019.The entire disclosures of all of the above-identified applications areincorporated herein by reference.

TECHNICAL FIELD

The present specification relates to the field of computer technologies,and in particular, to a verification method for user signing fastpayment with a bank card and an apparatus thereof.

BACKGROUND

With the continuous development of Internet technologies, onlineshopping has become a common shopping manner for general public. It isinevitable to resolve payment problems in online shopping. Currently,common payment methods include Internet banking payment and fastpayment. Because the fast payment method does not need to subscribe toInternet banking, and has a convenient and fast operation procedure anda higher security factor, it becomes popular quickly. Before the fastpayment is adopted, signing fast payment of a bank card needs to becompleted to generate a fast payment agreement. However, a userverification process is an important step in signing the fast payment ofthe bank card.

A common user verification manner may include that a user fills anapplication (such as a payment platform), with four essential elementsof a bank card that the user wants to sign in, that is, the name of theuser, a type of an identification (ID) of the user, an ID number of theuser, and a stored mobile phone number (to be specific, the mobile phonenumber that is stored when the user registers with the bank card). Thefour essential elements of the information are sent to a banking system,and the banking system delivers a short message service (SMS)verification code to the application after verification of the fouressential elements succeeds. The user fills the application, with theSMS verification code. The application sends the SMS verification codefilled by the user to the banking system. After the banking systemsuccessfully verifies the SMS verification code filled by the user,verification of the user is completed.

However, in the foregoing manner, in one aspect, the user needs to fillthe four essential elements, and switches between different applicationsto remember and fill the SMS verification code. The user interaction iscomplicated, and the user may remember the SMS verification codeincorrectly, resulting in a plurality of times of verification orunsuccessful verification and a poor user experience. In another aspect,in the foregoing user verification manner, both the verification of thefour essential elements and delivery and verification of the SMSverification code require a plurality of times of interaction with theapplication, the banking system, an operator server, and a platform thatsends and receives the SMS verification code. The high network latencyreduces the efficiency of the user verification. In a further aspect,due to the maturity of Internet crimes and popularization of criminaltools such as a rogue base station, crimes for purposefully stealinguser information and a card of the user emerge continuously. Therefore,data security in a user verification process needs to be improved.

SUMMARY

One or more embodiments of the present specification provide a userverification method and apparatus for signing a fast payment with a bankcard, to solve the problems in the existing technology that in a userverification process, the user interaction is complicated, and the usermay memorize an SMS verification code incorrectly, resulting in aplurality of times of verification or unsuccessful verification. Thehigh network latency reduces the efficiency of user verification andsecurity of data in a user verification process.

To solve the foregoing technical problems, the one or more embodimentsof the present specification are implemented as follows.

According to a first aspect, the one or more embodiments of the presentspecification provide A verification method. The method may comprise:performing, by an application, an account verification on accountinformation of a to-be-verified user; performing, by the application,based on a stored mobile phone number in the account information, amobile phone number verification on a user terminal in which theapplication is located if the account verification succeeds; sending, bythe application, an identification code of the application and thestored mobile phone number to a back-end server of the application ifthe mobile phone number verification succeeds, and sending averification request packet generated according to the identificationcode and basic information of the stored mobile phone number to a targetbase station; receiving, by the application, the verificationnotification returned by the back-end server, and determining, accordingto the verification notification, whether the verification of theto-be-verified user succeeds; and performing a fast payment signingprocess to generate a fast payment agreement when the verification ofthe to-be-verified user succeeds. The the target base station isconfigured to verify validity of the stored mobile phone numberaccording to the verification request packet, and send the verificationrequest packet to an operator server if the validity of the storedmobile phone number is verified. The operator server is configured toverify validity of the target base station, and forward the receivedverification request packet to the back-end server if the validity ofthe target base station is verified. The back-end server is configuredto perform a verification on the to-be-verified user to generate averification notification according to the verification request packetsent by the operator server, and the identification code and the storedmobile phone number sent by the application.

In one or more embodiments of the present specification, the performing,by the application, based on a stored mobile phone number in the accountinformation, a mobile phone number verification on a user terminal inwhich the application is located may comprise: obtaining, by theapplication, at least one mobile phone number of the user terminal inwhich the application is located; determining, by the application,whether the at least one mobile phone number of the user terminalcomprises the stored mobile phone number; and determining, by theapplication, in response to determining that the at least one mobilephone number of the user terminal comprises the stored mobile phonenumber, whether the mobile phone number verification of the userterminal succeeds.

In one or more embodiments of the present specification, the sending averification request packet generated according to the identificationcode and basic information of the stored mobile phone number to a targetbase station may comprise: assembling, by the application, the basicinformation of the stored mobile phone number and the identificationcode according to a preset format to generate the verification requestpacket; and sending, by the application, the verification request packetto the target base station.

In one or more embodiments of the present specification, the target basestation is configured to verify validity of the stored mobile phonenumber according to the verification request packet by: parsing, by thetarget base station, the verification request packet to obtain the basicinformation of the stored mobile phone number; obtaining, by the targetbase station, verification information of each candidate mobile phonenumber from the operator server, wherein the verification information ofeach candidate mobile phone number comprises basic information and stateinformation; matching, by the target base station, the stored mobilephone number with each candidate mobile phone number, and determining acandidate mobile phone number matching the stored mobile phone number asa to-be-compared mobile phone number; matching, by the target basestation, the basic information of the stored mobile phone number withbasic information of the to-be-compared mobile phone number, anddetermining state information of the to-be-compared mobile phone numberas state information of the stored mobile phone number if the basicinformation of the stored mobile phone number matches the basicinformation of the to-be-compared mobile phone number; determining, bythe target base station, according to the state information of thestored mobile phone number, whether the stored mobile phone number is ina preset state; and determining, in response to determining that thestored mobile phone number is in the preset state, whether the validityof the stored mobile phone number is verified.

In one or more embodiments of the present specification, the operatorserver is configured to verify validity of the target base station by:obtaining, by the operator server, verification information of thetarget base station; and determining, by the operator server, accordingto the verification information of the target base station andverification information of each candidate base station in the operatorserver, whether the validity of the target base station is verified.

In one or more embodiments of the present specification, the sending, bythe application, an identification code of the application and thestored mobile phone number to a back-end server of the application ifthe mobile phone number verification succeeds may comprise: displaying,by the application, an inquiry request about whether to perform theverification through the stored mobile phone number to theto-be-verified user if the mobile phone number verification succeeds;and receiving, by the application, response information of theto-be-verified user based on the inquiry request, and sending theidentification code of the application and the stored mobile phonenumber to the back-end server of the application if the responseinformation includes a confirmation message.

In one or more embodiments of the present specification, the back-endserver is configured to perform the verification on the to-be-verifieduser to generate the verification notification according to theverification request packet sent by the operator server and theidentification code and the stored mobile phone number sent by theapplication by: parsing, by the back-end server, the verificationrequest packet to obtain basic information of a stored mobile phonenumber corresponding to the verification request packet and anidentification code corresponding to the verification request packet;matching, by the back-end server, the stored mobile phone number and theidentification code corresponding to the verification request packetwith the stored mobile phone number and the identification code sent bythe application to generate a matching result; and determining, by theback-end server, the verification notification according to the matchingresult.

According to a second aspect, the one or more embodiments of the presentspecification provide a verification device. The verification device maycomprise: at least one processor; and a memory storingcomputer-executable instructions executable by the at least oneprocessor to cause the at least one processor to perform operationsincluding: performing, by an application, an account verification onaccount information of a to-be-verified user; performing, by theapplication, based on a stored mobile phone number in the accountinformation, a mobile phone number verification on a user terminal inwhich the application is located if the account verification succeeds;sending, by the application, an identification code of the applicationand the stored mobile phone number to a back-end server of theapplication if the mobile phone number verification succeeds, andsending a verification request packet generated according to theidentification code and basic information of the stored mobile phonenumber to a target base station; receiving, by the application, theverification notification returned by the back-end server, anddetermining, according to the verification notification, whether theverification of the to-be-verified user succeeds; and performing, by theapplication, a fast payment signing process to generate a fast paymentagreement when the verification of the to-be-verified user succeeds. Thetarget base station is configured to verify validity of the storedmobile phone number according to the verification request packet, andsend the verification request packet to an operator server if validityof the mobile phone number is verified, wherein the at least oneprocessor comprises the back-end server and the operator server. Theoperator server is configured to verify validity of the target basestation, and forward the received verification request packet to theback-end server if the validity of the target base station is verified.The back-end server is configured to perform a verification on theto-be-verified user to generate a verification notification according tothe verification request packet sent by the operator server, and theidentification code and the stored mobile phone number sent by theapplication.

According to another aspect, the one or more embodiments of the presentspecification provide a non-transitory computer-readable storage medium.The non-transitory computer-readable storage medium may store computerinstructions executable by at least one processor to cause the at leastone processor to perform operations. The operations may comprise:performing, by an application, an account verification on accountinformation of a to-be-verified user; performing, by the application,based on a stored mobile phone number in the account information, amobile phone number verification on a user terminal in which theapplication is located if the account verification succeeds; sending, bythe application, an identification code of the application and thestored mobile phone number to a back-end server of the application ifthe mobile phone number verification succeeds, and sending averification request packet generated according to the identificationcode and basic information of the stored mobile phone number to a targetbase station; receiving, by the application, the verificationnotification returned by the back-end server, and determining, accordingto the verification notification, whether the verification of theto-be-verified user succeeds; and performing, by the application, a fastpayment signing process to generate a fast payment agreement when theverification of the to-be-verified user succeeds. The target basestation is configured to verify validity of the stored mobile phonenumber according to the verification request packet, and send theverification request packet to an operator server if validity of themobile phone number is verified, wherein the at least one processorcomprises the back-end server and the operator server. The operatorserver is configured to verify validity of the target base station, andforward the received verification request packet to the back-end serverif the validity of the target base station is verified. The back-endserver is configured to perform a verification on the to-be-verifieduser to generate a verification notification according to theverification request packet sent by the operator server, and theidentification code and the stored mobile phone number sent by theapplication.

Technical solutions of the one or more embodiments of the presentspecification are adopted. After verification on account information ofa to-be-verified user by an application based on a banking systemsucceeds and verification on a mobile phone number of a user terminal bythe application succeeds, an identification code of the application anda stored mobile phone number are sent to a back-end server of theapplication, and a verification request packet generated according tothe identification code of the application and basic information of thestored mobile phone number is sent to a target base station. Aftervalidity of the stored mobile phone number is verified by the targetbase station based on the verification request packet, the verificationrequest packet is sent to an operator server by the target base station.After validity of the target base station is verified by the operatorserver, the verification request packet is forwarded to the back-endserver. The back-end server verifies the to-be-verified user accordingto the identification code and the stored mobile phone number that aresent by the application and the verification request packet sent by theoperator server, and the application determines, according to averification notification sent by the back-end server, whetherverification of the to-be-verified user succeeds. In an aspect, comparedwith the existing technology, only the account information needs to beprovided by the to-be-verified user in an entire verification process ofthe embodiments, to automatically verify the to-be-verified user. At thesame time, because there is no need for the to-be-verified user toswitch between different applications to remember and fill with an SMSverification code, which greatly simplifies interactive operations ofthe to-be-verified user, avoids a situation of memorizing the SMSverification code incorrectly, increases efficiency and a success rateof the verification, and has better user experience. In another aspect,in the foregoing verification process of the to-be-verified user,interactions between the application, the target base station, theoperator server, and the back-end server of the application are reduced,network latency is reduced, and efficiency of user check is improved. Ina further aspect, in the foregoing verification process, only through ajoint interaction and mutual restriction between the application, thetarget base station, the operator server, and the back-end server, theto-be-verified user can be verified, so as to improve security of datain the entire verification process.

BRIEF DESCRIPTION OF THE DRAWINGS

To describe one or more embodiments of the present specification or thetechnical solutions in the existing technology more clearly, theaccompanying drawings required for describing the embodiments of thepresent specification or the existing technology are briefly introducedas follows. Apparently, the accompanying drawings in the followingdescription show merely some embodiments in one or more embodiments ofthe present specification, and a person of ordinary skill in the art maystill derive other drawings from these accompanying drawings withoutcreative efforts.

FIG. 1 is a schematic diagram of an application scenario of a userverification method for signing a fast payment with a bank card,according to one or more embodiments of the present specification.

FIG. 2 is a flowchart of a user verification method for signing a fastpayment with a bank card, according to one or more embodiments of thepresent specification.

FIG. 3 is a flowchart of verifying, by a target base station, validityof a stored mobile phone number according to a verification requestpacket, according to one or more embodiments of the presentspecification.

FIG. 4 is a flowchart of a user verification method for signing a fastpayment with a bank card, according to one or more embodiments of thepresent specification.

FIG. 5 is a flowchart of a user verification method for signing a fastpayment with a bank card, according to one or more embodiments of thepresent specification.

FIG. 6 is a structural block diagram of a user verification apparatusfor signing a fast payment with a bank card, according to one or moreembodiments of the present specification.

FIG. 7 is a structural block diagram of a user verification apparatusfor signing a fast payment with a bank card, according to one or moreembodiments of the present specification.

FIG. 8 is a schematic diagram of a user verification device for signinga fast payment with a bank card, according to an embodiment of thepresent specification.

DETAILED DESCRIPTION OF THE INVENTION

One or more embodiments of the present specification provide a userverification method and an apparatus for signing a fast payment with abank card, to solve problems in the existing technology that in a userverification process, a user interaction is complicated, and the usermay memorize an SMS verification code incorrectly. It may result in aplurality of times of verification or unsuccessful verification, and ahigh network latency which reduce the efficiency of user verificationand security of data in a user verification process.

For a person skilled in the art to understand the technical solutions inone or more embodiments of the present specification better, thefollowing description clearly and completely describes the technicalsolutions in the one or more embodiments of the present specificationwith reference to the accompanying drawings in the one or moreembodiments of the present specification. Apparently, the describedembodiments are merely some but not all of the embodiments of thepresent specification. All other embodiments obtained by a person ofordinary skill in the art based on the one or more embodiments of thepresent specification without creative efforts shall fall within theprotection scope of the one or more embodiments of the presentspecification.

FIG. 1 is a schematic diagram of an application scenario of a userverification method for signing a fast payment with a bank card,according to one or more embodiments of the present specification. Asshown in FIG. 1, an application 101 (for example, a payment-typeapplication) obtains account information of a to-be-verified user, andsends the account information to a banking system 102. The bankingsystem 102 performs an account verification on the account information,and sends a notification of a successful account verification to theapplication 101 if the account verification succeeds. The application101 receives and responds to the notification of successful accountverification, and performs, based on a stored mobile phone number in theaccount information, a mobile phone number verification on a userterminal 103 in which the application 101 is located, that is,determines whether mobile phone numbers in the user terminal 103 includethe stored mobile phone number. If the mobile phone numbers in the userterminal 103 include the stored mobile phone number, it is determinedthat the mobile phone number verification of the user terminal 103succeeds. If the mobile phone numbers in the user terminal 103 do notinclude the stored mobile phone number, it is determined that the mobilephone number verification of the user terminal 103 fails. Theapplication 101 sends an identification code of the application 101 andthe stored mobile phone number to a back-end server 104 of theapplication 101 if the mobile phone number verification succeeds,generates a verification request packet according to the identificationcode of the application 101 and basic information of the stored mobilephone number, and sends the verification request packet to a target basestation 105. The target base station 105 verifies validity of the storedmobile phone number based on the verification request packet, and thetarget base station 105 sends the verification request packet to anoperator server 106 if the verification succeeds. The operator server106 verifies validity of the target base station 105, and the operatorserver 106 sends the verification request packet to the back-end server104 if the verification succeeds. The back-end server 104 verifies theto-be-verified user according to the identification code of theapplication 101, the stored mobile phone number sent by the application101, and the verification request packet sent by the operator server106, and sends a verification notification to the application 101. Theapplication 101 determines, according to the verification notification,whether verification of the to-be-verified user succeeds. After theverification of the to-be-verified user succeeds, a fast payment signingprocess may be performed, to generate a fast payment agreement.

FIG. 2 is a schematic flowchart of a user verification method forsigning a fast payment with a bank card, according to one or moreembodiments of the present specification. As shown in FIG. 2, the methodmay include the following steps.

In Step S202, an application performs an account verification on accountinformation of a to-be-verified user based on a banking system.

In the embodiment, the application receives and responds to a userverification request based on signing the fast payment with the bankcard, provides the to-be-verified user with an account information inputpage for the to-be-verified user to input the account information on theaccount information input page, and obtains the account information ofthe to-be-verified user from the account information input page. Theaccount information may refer to information input by the to-be-verifieduser when registering a bank card, and the account information of theto-be-verified user may include the name of the to-be-verified user, thetype of the identification of the to-be-verified user (for example, anID card or a military ID card), the number of the identification of theto-be-verified user (for example, an ID number or a military ID number),a stored mobile phone number (such as, a mobile phone number stored whenregistering a bank card), or the like, which is not specifically limitedin the embodiment. The account information of the to-be-verified user issent to the banking system, wherein the banking system herein refers toa banking system corresponding to the bank card corresponding to theaccount information. The banking system compares the account informationof the to-be-verified user with the account information stored in thebanking system by the to-be-verified user when registering the bankcard. If the comparison is successful, such that the acquired accountinformation matches the stored account information, it is determinedthat the account verification of the account information of theto-be-verified user succeeds, and a notification of a successful accountverification is sent to the application. If the comparison is notsuccessful, such that the acquired account information does not matchthe stored account information, it is determined that the accountverification of the account information of the to-be-verified userfails, and a notification of an unsuccessful account verification issent to the application.

It should be noted that the application may include a payment-typeapplication or the like, which is not specifically limited in theembodiment.

In Step S204, the application performs, based on a stored mobile phonenumber in the account information, a mobile phone number verification ona user terminal in which the application is located if the accountverification succeeds.

In the embodiment of the present specification, if the applicationreceives a notification of a successful account verification returned bya banking system, it is determined that the account verificationsucceeds. The application, based on a stored mobile phone number in theaccount information, performs a mobile phone number verification on theuser terminal in which the application is located, may include:obtaining, by the application, mobile phone numbers in the user terminalin which the application is located (that is, the user terminal in whichthe application is installed); determining, by the application, whetherthe mobile phone numbers in the user terminal include the stored mobilephone number; and determining, according to a determination result,whether the mobile phone number verification of the user terminalsucceeds. Specifically, if there is only one mobile phone number in theuser terminal, whether the mobile phone number is the same as the storedmobile phone number is determined. If the mobile phone number is thesame as the stored mobile phone number, it is determined that the mobilephone number verification of the user terminal succeeds. If the mobilephone number is different from the stored mobile phone number, it isdetermined that the mobile phone number verification of the userterminal fails. If there are a plurality of mobile phone numbers in theuser terminal, whether the mobile phone numbers in the user terminalinclude a mobile phone number same as the stored mobile phone number isdetermined. If the mobile phone numbers in the user terminal include amobile phone number same as the stored mobile phone number, it isdetermined that the mobile phone number verification of the userterminal succeeds. If the mobile phone numbers in the user terminal donot include a mobile phone number same as the stored mobile phonenumber, it is determined that the mobile phone number verification ofthe user terminal fails.

It can be learned from the above that, based on the stored mobile phonenumber, verifying the mobile phone numbers on the user terminal in whichthe application is located, may include determining whether the mobilephone numbers in the user terminal include the stored mobile phonenumber. When the mobile phone numbers in the user terminal include thestored mobile phone number, a further verification may be performed toavoid a situation that criminals misuse the stored mobile phone numberfor the verification, and to ensure the data security in theverification of the to-be-verified user.

In Step S206, the application sends an identification code of theapplication and the stored mobile phone number to a back-end server ofthe application if the mobile phone number verification succeeds, andsends a verification request packet generated according to theidentification code and basic information of the stored mobile phonenumber to a target base station.

In the embodiment of the present specification, the application may sendthe identification code of the application and the stored mobile phonenumber to the back-end server of the application through mobile data ofthe user terminal if the mobile phone number verification of the userterminal succeeds, assemble the basic information of the stored mobilephone number and the identification code of the application according toa preset format to generate a verification request packet, and send theverification request packet to the target base station. The basicinformation of the stored mobile phone number may include the storedmobile phone number and SIM card information corresponding to the storedmobile phone number. When the application accesses an operator server(i.e., an operator server of the stored mobile phone number), an APPID(an application identity) or an APPKEY (an application key) may beobtained as a unique identifier for identifying the application to theoperator server. Therefore, the APPID and/or the APPKEY may be used asthe identification code of the application. It should be noted that theidentification code of the application is not limited thereto. Thepreset format may be set according to a format requirement of a packetreceived by the target base station. It should be noted that the targetbase station may refer to a base station that receives the verificationrequest packet.

Further, to improve the user experience, if the mobile phone numberverification succeeds, sending, by the application, an identificationcode of the application and the stored mobile phone number to a back-endserver of the application may include: displaying, by the application,an inquiry request about whether to verify through the stored mobilephone number to a to-be-verified user if the mobile phone numberverification succeeds; receiving, by the application, an responseinformation, responding to the inquiry request from the to-be-verifieduser; and sending the identification code of the application and thestored mobile phone number to the back-end server of the application ifthe response information is confirmation information.

In the embodiment of the present specification, the application maygenerate and display the inquiry request about whether to verify throughthe stored mobile phone number if the mobile phone number verificationsucceeds, and the inquiry request may be displayed in a form of a text,a picture, or the like, which is not specifically limited in theembodiment. The to-be-verified user makes an answering operation basedon the inquiry request, and the application responds to the answeringoperation to obtain the response information. The identification code ofthe application and the stored mobile phone number are sent to theback-end server of the application if the response information is theconfirmation information.

It can be learned from the above that, after the mobile phone numberverification succeeds, by generating and displaying the inquiry request,and making a corresponding operation according to the responseinformation of the to-be-verified user based on the inquiry request,whether to perform a next operation according to intention of theto-be-verified user may be determined, thereby improving the userexperience.

In Step S208, the target base station verifies validity of the storedmobile phone number according to the verification request packet, andsends the verification request packet to the operator server if thevalidity of the stored mobile phone number is verified.

In the embodiment of the present specification, FIG. 3 is a flowchart ofverifying, by a target base station, validity of a stored mobile phonenumber according to a verification request packet, according to one ormore embodiments of the present specification. As shown in FIG. 3, thefollowing steps may be included.

In Step S302, a target base station parses a verification requestpacket, to obtain the basic information of the stored mobile phonenumber.

In the embodiment of the present specification, a process of parsing, bythe target base station, the verification request packet may includedisassembling the verification request packet according to an assemblingmanner of the verification request packet, to obtain the basicinformation of the stored mobile phone number. It should be noted thatthe basic information of the stored mobile phone number has beendescribed above, and therefore the details are not described hereinagain.

In Step S304, the target base station obtains verification informationof each candidate mobile phone number from the operator server to whichthe target base station belongs, where the verification information ofeach candidate mobile phone number includes the basic information andstate information.

In the embodiment of the present specification, the verificationinformation of each candidate mobile phone number is obtained from theoperator server to which the target base station belongs (i.e., theoperator server of the stored mobile phone number), and the verificationinformation of each candidate mobile phone number may include the basicinformation and the state information. The basic information of acandidate mobile phone number may include a candidate mobile phonenumber and the SIM card information corresponding to the candidatemobile phone number, and the state information of the candidate mobilephone number may include permission information of each function of thecandidate mobile phone number, such as the permission to make andreceive a call, the permission to send and read an SMS message, or thelike, which is not specifically limited in the embodiment. It should benoted that the candidate mobile phone number herein refers to a mobilephone number stored in the operator server. For purpose ofdistinguishing herein, the mobile phone numbers stored in the operatorserver are named as the candidate mobile phone numbers.

In Step S306, the target base station matches the stored mobile phonenumber with the candidate mobile phone numbers, and determine acandidate mobile phone number matching the stored mobile phone number asa to-be-compared mobile phone number, that is, determine the candidatemobile phone number same as the stored mobile phone number as theto-be-compared mobile phone number.

In Step S308, the target base station matches the basic information ofthe stored mobile phone number with basic information of theto-be-compared mobile phone number, and if the basic information of thestored mobile phone number matches the basic information of theto-be-compared mobile phone number, determine the state information ofthe to-be-compared mobile phone number as state information of thestored mobile phone number.

In the embodiment of the present specification, corresponding data inthe basic information of the stored mobile phone number is matched withcorresponding data in the basic information of the to-be-compared mobilephone number. If the corresponding data in the basic information of thestored mobile phone number and the corresponding data in the basicinformation of the to-be-compared mobile phone number are matched, thestate information of the to-be-compared mobile phone number isdetermined as the state information of the stored mobile phone number.

In Step S310, the target base station determines, according to the stateinformation of the stored mobile phone number, whether the stored mobilephone number is in a preset state, and determine, according to adetermination result, whether the validity of the stored mobile phonenumber is verified.

In the embodiment of the present specification, the preset state may becustomized, which is not specifically limited in the embodiment. Forexample, the preset state may be the permission to make and receive acall, the permission to send and read an SMS message, and the permissionto access the internet through mobile data. Whether the stored mobilephone number is in the preset state may be determined according to thepermission information of each function in the state information of thestored mobile phone number. If the stored mobile phone number is in thepreset state, it is determined that validity of the stored mobile phonenumber is verified. If the stored mobile phone number is not in thepreset state, it is determined that the verification of the validity ofthe stored mobile phone number fails.

It can be learned from the above that, the validity of the stored mobilephone number in the verification request packet may be verified toensure that the stored mobile phone number is valid, and further ensurethe data security in the verification process.

In Step S210, the operator server verifies validity of the target basestation, and forwards the received verification request packet to theback-end server if the validity is verified.

In the embodiment of the present specification, after receiving theverification request packet sent by the target base station, theoperator server verifies the validity of the target base station. Aprocess of verifying the validity of the target base station mayinclude: obtaining, by the operator server, verification information ofthe target base station; and verifying, according to the verificationinformation of the target base station and verification information ofeach candidate base station in the operator server, validity of thetarget base station. The verification information of the target basestation may include location information of the target base station,service state information of the target base station, performanceparameters of the target base station, and the like, which is notspecifically limited in the embodiment. The verification information ofthe candidate base station may include location information of thecandidate base station, service state information of the candidate basestation, performance parameters of the candidate base station, and thelike, which is not specifically limited in the embodiment. It should benoted that the operator server stores verification information of allbase stations related to the operator server. For purpose ofdistinguishing herein, the base stations related to the operator serverare named as the candidate base stations. The operator server obtainsthe verification information of the target base station from the targetbase station, and matches the verification information of the targetbase station with the verification information of each candidate basestation in the operator server. If there is a candidate base station ofwhich verification information matches the verification information ofthe target base station in the operator server, it is determined thatthe validity of the target base station is verified. If there is nocandidate base station of which verification information matches theverification information of the target base station in the operatorserver, it is determined that the verification of the validity of thetarget base station fails.

It can be learned from the above that, the validity of the target basestation is verified, and after the validity is verified, a nextverification step is performed to ensure the validity of the target basestation, thereby avoiding a situation that a rogue base station sendsthe verification request packet to the operator server, and furtherensuring data security in the entire verification process.

In Step S212, the back-end server verifies a to-be-verified useraccording to the verification request packet sent by the operator serverand the identification code and the stored mobile phone number sent bythe application.

In the embodiment of the present specification, the back-end serverparses the verification request packet sent by the operator server, toobtain the basic information of a stored mobile phone numbercorresponding to the verification request packet and an identificationcode corresponding to the verification request packet. The back-endserver matches the stored mobile phone number corresponding to theverification request packet and the stored mobile phone number sent bythe application, and matches the identification code corresponding tothe verification request packet and the identification code sent by theapplication. If the stored mobile phone number corresponding to theverification request packet is the same as the stored mobile phonenumber sent by the application and the identification code correspondingto the verification request packet is the same as the identificationcode sent by the application, it is determined that the verification ofthe to-be-verified user succeeds, a verification notification of asuccessful verification is generated, and the verification notificationof the successful verification is sent to the application. If the storedmobile phone number corresponding to the verification request packet isdifferent from the stored mobile phone number sent by the applicationand/or the identification code corresponding to the verification requestpacket is different from the identification code sent by theapplication, it is determined that verification of the to-be-verifieduser fails, a verification notification of an unsuccessful verificationis generated, and the verification notification of the unsuccessfulverification is sent to the application.

In Step S214, the application receives a verification notificationreturned by the back-end server, and determines, according to theverification notification, whether the verification of theto-be-verified user succeeds.

In the embodiment of the present specification, the application receivesthe verification notification returned by the back-end server. If theverification notification is a verification notification of a successfulverification, it is determined that the verification of theto-be-verified user succeeds. If the verification notification is averification notification of an unsuccessful verification, it isdetermined that the verification of the to-be-verified user fails.

Compared with the existing technology, in the foregoing entireverification process, only the account information needs to be providedby the to-be-verified user to automatically verify the to-be-verifieduser. At the same time, because there is no need for the to-be-verifieduser to switch between different applications to remember and fill anSMS verification code, the interactive operation of the to-be-verifieduser is greatly simplified for avoiding a situation of incorrectlyremembering the SMS verification code, thereby increasing efficiency anda success rate of the verification, and a better user experience. Inaddition, in the foregoing verification process of the to-be-verifieduser, the interaction between the application, the target base station,the operator server, and the back-end server of the application isreduced, the network latency is reduced, and the efficiency of userverification is improved. Moreover, in the foregoing verificationprocess, only after the verifications of the account information and themobile phone number of the user terminal by the application succeed, thevalidity of the stored mobile phone number is verified by the targetbase station, and the validity of the target base station is verified bythe operator server, the back-end server may verify the to-be-verifieduser. To be specific, only through a joint interaction and a mutualrestriction among the application, the target base station, the operatorserver, and the back-end server, the to-be-verified user can be checked,so as to improve the data security of the entire verification process.

It should be noted that when the to-be-verified user does not agree touse the stored mobile phone number to perform the verification, or theverification of the to-be-verified user fails because of theverification failure in any one of the foregoing verification steps, arisk assessment may be performed on the user terminal corresponding tothe stored mobile phone number. After the risk assessment succeeds, andthe verification of the four essential information elements of thebanking system succeeds, the to-be-verified user is verified by sendinga verification code to the stored mobile phone number. It should benoted that a process of performing the risk assessment on the userterminal corresponding to the stored mobile phone number may include:obtaining the device information of the user terminal corresponding tothe stored mobile phone number; determining, according to the deviceinformation of the user terminal, a change frequency and a change timeof the user terminal in which the stored mobile phone number is located;obtaining the location information of the network login of the userterminal corresponding to the stored mobile phone number, to determinewhether there is a location abnormality of the user terminalcorresponding to the stored mobile phone number; and finally, performingthe risk assessment on the user terminal according to the changefrequency and the change time of the user terminal and the locationabnormality.

FIG. 4 is a flowchart of a user verification method for signing a fastpayment with a bank card, according to one or more embodiments of thepresent specification. The method may be applied to an application, andthe application may be, for example, a payment-type application, whichis not specifically limited in the embodiment. As shown in FIG. 4, themethod may include the following steps.

In Step S402, an application verifies account information of ato-be-verified user based on a banking system. An implementation processof Step S402 has been described in Step S202 in the above, and thereforethe details are not described herein again.

In Step S404, the application performs, based on a stored mobile phonenumber in the account information, a mobile phone number verification ona user terminal in which the application is located if the accountverification succeeds.

In the embodiment of the present specification, the performing, based ona stored mobile phone number in the account information, a mobile phonenumber verification on a user terminal in which the application islocated may include: obtaining mobile phone numbers in the user terminalin which the application is located; determining whether the mobilephone numbers in the user terminal include the stored mobile phonenumber; and determining, according to a determining result, whether themobile phone number verification of the user terminal succeeds.

An implementation process of Step S404 has been described in Step S204above, and therefore the details are not described herein again.

In Step S406, the application sends an identification code of theapplication and the stored mobile phone number to a back-end server ofthe application if the mobile phone number verification succeeds, andsend a verification request packet generated according to theidentification code and basic information of the stored mobile phonenumber to a target base station.

In the embodiment of the present specification, the sending averification request packet generated according to the identificationcode and basic information of the stored mobile phone number to a targetbase station may include: assembling the basic information of the storedmobile phone number and the identification code according to a presetformat to generate the verification request packet; and sending theverification request packet to the target base station.

It should be noted that an implementation process of Step S406 has beendescribed in Step S206 in the above, and therefore the details are notdescribed herein again.

Further, to improve the user experience, the sending an identificationcode of the application and the stored mobile phone number to a back-endserver of the application if the mobile phone number verificationsucceeds may include: displaying an inquiry request about whether toperform the verification through the stored mobile phone number to ato-be-verified user if the mobile phone number verification succeeds;receiving response information of the to-be-verified user based on theinquiry request; and sending the identification code of the applicationand the stored mobile phone number to the back-end server of theapplication if the response information is confirmation information. Itshould be noted that the process has been described in detail above, andtherefore the details are not described herein again.

In Step S408, the application receives a verification notification forthe to-be-verified user returned by the back-end server according to theidentification code of the application and the stored mobile phonenumber that are received and the verification request packet forwardedby the target base station and an operator server.

In the embodiment of the present specification, in Step S406, after theapplication sends the verification request packet to the target basestation, the target base station verifies validity of the stored mobilephone number according to the verification request packet, and sends theverification request packet to the operator server after the validity ofthe stored mobile phone number is verified. After receiving theverification request packet sent by the target base station, theoperator server verifies validity of the target base station, and sendsthe verification request packet to the back-end server of theapplication after the validity of the target base station is verified.The back-end server parses the verification request packet to obtain thebasic information of a stored mobile phone number that corresponds tothe verification request packet and an identification code thatcorresponds to the verification request packet, matches the storedmobile phone number corresponding to the verification request packetwith the stored mobile phone number sent by the application, and matchesthe identification code corresponding to the verification request packetwith the identification code sent by the application. If the storedmobile phone number corresponding to the verification request packetmatches the stored mobile phone number sent by the application, and theidentification code corresponding to the verification request packetmatches the identification code sent by the application, it isdetermined that the verification of the to-be-verified user succeeds, averification notification of a successful verification is generated, andthe verification notification of the successful verification is sent tothe application. If the stored mobile phone number corresponding to theverification request packet does not match the stored mobile phonenumber sent by the application, and/or the identification codecorresponding to the verification request packet does not match theidentification code sent by the application, it is determined that theverification of the to-be-verified user fails, a verificationnotification of an unsuccessful verification is generated, and theverification notification of the unsuccessful check is sent to theapplication.

In Step S410, the application determines, according to the verificationnotification, whether the verification of the to-be-verified usersucceeds.

In the embodiment of the present specification, if the receivedverification notification sent by the back-end server is a verificationnotification of a successful verification, it is determined thatverification of the to-be-verified user succeeds. If the receivedverification notification sent by the back-end server is a verificationnotification of an unsuccessful verification, it is determined thatverification of the to-be-verified user fails.

Compared with the existing technology, in the entire verificationprocess of the embodiment, only the account information needs to beprovided by the to-be-verified user for automatically verifying theto-be-verified user. At the same time, because there is no need for theto-be-verified user to switch between different applications to rememberand fill an SMS verification code, the interactive operation of theto-be-verified user is greatly simplified for avoiding a situation ofincorrectly remembering the SMS verification code, increasing theefficiency and a success rate of the verification, and better userexperience. In addition, in the foregoing verification process of theto-be-verified user, the interaction among the application, the targetbase station, the operator server, and the back-end server of theapplication is reduced, the network latency is reduced, and theefficiency of the user verification is improved. Moreover, in theforegoing verification process, only through the joint interaction andmutual restriction among the application, the target base station, theoperator server, and the back-end server, the to-be-verified user can beverified, so as to improve the data security of the entire checkprocess.

FIG. 5 is a flowchart of a user verification method for signing a fastpayment with a bank card, according to one or more embodiments of thepresent specification. The method may be applied to a back-end server ofan application. As shown in FIG. 5, the method may include the followingsteps.

In Step S502, a back-end server receives an identification code of theapplication and a stored mobile phone number that are sent by theapplication.

In the embodiment of the present specification, the application performsan account verification on the account information of a to-be-verifieduser based on a banking system. After the account verification succeeds,the application performs, based on a stored mobile phone number in theaccount information, a mobile phone number verification on a userterminal in which the application is located. After the mobile phonenumber verification succeeds, the application sends the identificationcode of the application and the stored mobile phone number to a back-endserver of the application. The back-end server receives theidentification code of the application and the stored mobile phonenumber.

In Step S504, the back-end server receives a verification request packetsent by the application, a target base station, and an operator server,wherein the verification request packet is generated according to theidentification code of the application and the basic information of thestored mobile phone number.

In the embodiment of the present specification, when sending the storedmobile phone number and the identification code of the application tothe back-end server, the application generates the verification requestpacket according to the basic information of the stored mobile phonenumber and the identification code of the application, and sends theverification request packet to the target base station. The target basestation verifies validity of the stored mobile phone number based on theverification request packet, and sends the verification request packetto the operator server after the validity of the stored mobile phonenumber is verified. The operator server verifies validity of the targetbase station, and sends the verification request packet to the back-endserver after the validity of the target base station is verified. Theback-end server receives the verification request packet sent by theoperator server.

In Step S506, the back-end server verifies a to-be-verified useraccording to the identification code of the application and the storedmobile phone number sent by the application and the verification requestpacket.

In the embodiment of the present specification, first, the verificationrequest packet is parsed to obtain information of a stored mobile phonenumber that corresponds to the verification request packet and anidentification code that corresponds to the verification request packet.Then, the stored mobile phone number and the identification codecorresponding to the verification request packet are matched with thestored mobile phone number and the identification code of theapplication sent by the application, respectively. Finally, averification notification is determined according to a matching result.Specifically, matching between the stored mobile phone numbercorresponding to the verification request packet and the stored mobilephone number sent by the application and matching between theidentification code corresponding to the verification request packet andthe identification code sent by the application are performed. If thestored mobile phone number corresponding to the verification requestpacket and the stored mobile phone number sent by the application matchand the identification code corresponding to the verification requestpacket and the identification code sent by the application match, it isdetermined that the verification of the to-be-verified user succeeds,and a verification notification of a successful verification isgenerated. If the stored mobile phone number corresponding to theverification request packet and the stored mobile phone number sent bythe application do not match and/or the identification codecorresponding to the verification request packet and the identificationcode sent by the application do not match, it is determined thatverification of the to-be-verified user fails, and a verificationnotification of an unsuccessful verification is generated.

In Step S508, the back-end server sends a verification notification tothe application. In the embodiment of the present specification, theverification notification is sent to the application, and theapplication determines, according to the verification notification,whether the verification of the to-be-verified user succeeds.

In the foregoing verification process of the to-be-verified user,interactions among the application, the target base station, theoperator server, and the back-end server of the application are reduced,the network latency is reduced, and the efficiency of user verificationis improved. In addition, in the foregoing verification process, onlythrough a joint interaction and mutual restriction among theapplication, the target base station, the operator server, and theback-end server, the to-be-verified user can be verified, so as toimprove data security of the entire verification process.

Corresponding to the foregoing user verification method based on signingfast payment of the bank card in FIG. 4, based on a same principle, anembodiment of the present specification further provides a userverification apparatus for signing a fast payment with a bank cardapplied to an application. FIG. 6 is a structural block diagram of auser verification apparatus for signing a fast payment with a bank card,according to one or more embodiments of the present specification. Asshown in FIG. 6, the user verification apparatus 600 based on signingthe fast payment of the bank card may include a first verificationmodule 601, a second verification module 602, a sending module 603, areceiving module 604, and a determining module 605.

Wherein, the first verification module 601 may be configured to verifyaccount information of a to-be-verified user based on a banking system.

The second verification module 602 may be configured to perform, basedon a stored mobile phone number in the account information, a mobilephone number verification on a user terminal in which the application islocated if the account verification succeeds.

The sending module 603 may be configured to send an identification codeof the application and the stored mobile phone number to a back-endserver of the application if the mobile phone number verificationsucceeds, and send a verification request packet generated according tothe identification code and basic information of the stored mobile phonenumber to a target base station.

The receiving module 604 may be configured to receive a verificationnotification for the to-be-verified user returned by the back-end serveraccording to the received identification code of the application and thestored mobile phone number and the verification request packet forwardedby the target base station and an operator server.

The determining module 605 may be configured to determine, according tothe verification notification, whether verification of theto-be-verified user succeeds.

Further, the second verification module 602 may be configured to obtainmobile phone numbers in the user terminal in which the application islocated, determine whether the mobile phone numbers in the user terminalinclude the stored mobile phone number, and determine, according to adetermining result, whether the mobile phone number verification of theuser terminal succeeds.

Further, the sending module 603 may be configured to assemble the basicinformation of the stored mobile phone number and the identificationcode according to a preset format to generate the verification requestpacket, and send the verification request packet to the target basestation.

Furthermore, the sending module 603 may be configured to display aninquiry request about whether to perform the verification through thestored mobile phone number to the to-be-verified user if the mobilephone number verification succeeds, receive response information fromthe to-be-verified user based on the inquiry request, and send theidentification code of the application and the stored mobile phonenumber to the back-end server of the application if the responseinformation is confirmation information.

According to the user verification apparatus based on signing the fastpayment with the bank card provided in the embodiment of the presentspecification, compared with the existing technology, in the embodiment,only the account information needs to be provided by the to-be-verifieduser in the entire verification process for automatically verifying theto-be-verified user. At the same time, because there is no need for theto-be-verified user to switch between different applications to rememberand fill an SMS verification code, the interactive operation of theto-be-verified user is greatly simplified for avoiding a situation ofincorrectly remembering the SMS verification code, thereby increasingthe efficiency and a success rate of the verification, and a better userexperience. In addition, in the foregoing verification process of theto-be-verified user, the interactions among the application, the targetbase station, the operator server, and the back-end server of theapplication are reduced, the network latency is reduced, and theefficiency of the user verification is improved. Moreover, in theforegoing verification process, only through a joint interaction andmutual restriction among the application, the target base station, theoperator server, and the back-end server, the to-be-verified user can beverified, so as to improve data security of the entire verificationprocess.

Corresponding to the foregoing user verification method based on signingthe fast payment of the bank card in FIG. 5, based on a same principle,an embodiment of the present specification further provides a userverification apparatus for signing a fast payment with a bank card,applied to a back-end server of an application. FIG. 7 is a structuralblock diagram of a user verification apparatus for signing a fastpayment with a bank card, according to one or more embodiments of thepresent specification. As shown in FIG. 7, the user verificationapparatus 700 based on signing the fast payment of the bank card mayinclude a first receiving module 701, a second receiving module 702, averification module 703, and a notification sending module 704.

Wherein, the first receiving module 701 may be configured to receive anidentification code of the application and a stored mobile phone numberthat are sent by the application.

The second receiving module 702 may be configured to receive averification request packet sent by the application, a target basestation, and an operator server, wherein the verification request packetis generated according to the identification code of the application andbasic information of the stored mobile phone number.

The verification module 703 may be configured to verify a to-be-verifieduser according to the identification code of the application and thestored mobile phone number that are sent by the application and theverification request packet.

The notification sending module 704 may be configured to send averification notification to the application.

Further, the verification module 703 may include:

a parsing unit, configured to parse the verification request packet toobtain basic information of a stored mobile phone number thatcorresponds to the verification request packet and an identificationcode that corresponds to the verification request packet;

a matching unit, configured to match the stored mobile phone number andthe identification code that correspond to the verification requestpacket with the identification code of the application and the storedmobile phone number that are sent by the application, respectively; and

a determining unit, configured to determine a verification notificationaccording to a matching result.

According to the user verification apparatus based on signing the fastpayment of the bank card provided in the embodiment of the presentspecification, in the foregoing verification process of theto-be-verified user, the interactions among the application, the targetbase station, the operator server, and the back-end server of theapplication are reduced, the network latency is reduced, and theefficiency of the user verification is improved. In addition, in theforegoing verification process, only through the joint interaction andmutual restriction among the application, the target base station, theoperator server, and the back-end server, the to-be-verified user can beverified, so as to improve data security of the entire verificationprocess.

Further, based on the foregoing method shown in FIG. 4, an embodiment ofthe present specification further provides a user verification devicefor signing a fast payment with a bank card. FIG. 8 is a schematicstructural diagram of a user verification device for signing a fastpayment with a bank card, according to an embodiment of the presentspecification. The device is configured to execute the foregoing userverification method based on the method of signing the fast payment ofthe bank card shown in FIG. 4.

As shown in FIG. 8, the user verification device based on signing thefast payment of the bank card may vary a lot due to differentconfigurations or different performances, and may include one or more ofthe processors 801 and a memory 802. The memory 802 may store one ormore application programs or data. The memory 802 may include atransient storage or a persistent storage. The application programstored in the memory 802 may include one or more modules (not shown inthe figure), and each module may include a series of computer-executableinstructions in the user verification device based on signing the fastpayment of the bank card. Furthermore, the processor 801 may beconfigured to communicate with the memory 802, and execute, on the userverification device based on signing the fast payment of the bank card,the series of computer-executable instructions in the memory 802. Theuser verification device based on signing the fast payment of the bankcard may further include one or more of the power supply 803, one ormore of the wired or wireless network interface 804, one or more of theinput/output interface 805, one or more of the keyboard 806, and thelike.

In a specific embodiment, the user verification device based on signingthe fast payment of the bank card includes a memory, and one or moreprograms, wherein the one or more programs are stored in the memory andmay include one or more modules, and each module may include a series ofcomputer-executable instructions in a user verification device. The oneor more programs are configured to be executed by one or moreprocessors, and include the computer-executable instructions used forperforming the following operations:

verifying account information of a to-be-verified user based on abanking system;

performing, based on a stored mobile phone number in the accountinformation, a mobile phone number verification on a user terminal inwhich the application is located if the account verification succeeds;

sending an identification code of the application and the stored mobilephone number to a back-end server of the application if the mobile phonenumber verification succeeds, and sending a verification request packetgenerated according to the identification code and basic information ofthe stored mobile phone number to a target base station;

receiving a verification notification for the to-be-verified userreturned by the back-end server according to the identification code ofthe application and the stored mobile phone number that are received andthe verification request packet forwarded by the target base station andan operator server; and

determining, according to the verification notification, whetherverification of the to-be-verified user succeeds.

Further, when the computer-executable instructions are executed, theperforming, based on a stored mobile phone number in the accountinformation, a mobile phone number verification on a user terminal inwhich the application is located includes:

obtaining mobile phone numbers in the user terminal in which theapplication is located; and

determining whether the mobile phone numbers in the user terminalinclude the stored mobile phone number, and determining, according to adetermining result, whether the mobile phone number verification of theuser terminal succeeds.

Further, when the computer-executable instructions are executed, thesending a verification request packet generated according to theidentification code and basic information of the stored mobile phonenumber to a target base station includes:

assembling the basic information of the stored mobile phone number andthe identification code according to a preset format, to generate theverification request packet; and

sending the verification request packet to the target base station.

Further, when the computer-executable instructions are executed, thesending an identification code of the application and the stored mobilephone number to a back-end server of the application if the mobile phonenumber verification succeeds includes:

displaying an inquiry request about whether to perform the verificationthrough the stored mobile phone number to the to-be-verified user if themobile phone number verification succeeds; and

receiving response information of the to-be-verified user based on theinquiry request, and sending the identification code of the applicationand the stored mobile phone number to the back-end server of theapplication if the response information is confirmation information.

According to the user response device based on signing the fast paymentof the bank card provided in the embodiment of the presentspecification, compared with the existing technology, in the embodiment,only the account information needs to be provided by the to-be-verifieduser in the entire verification process to automatically verify theto-be-verified user. At the same time, because there is no need for theto-be-verified user to switch between different applications to rememberand fill with an SMS verification code, an interactive operation of theto-be-verified user is greatly simplified, a situation of incorrectlyremembering the SMS verification code is avoided, the efficiency and asuccess rate of the verification are increased, and the user experienceis improved. In addition, in the foregoing verification process of theto-be-verified user, interactions among the application, the target basestation, the operator server, and the back-end server of the applicationare reduced, the network latency is reduced, and the efficiency of userverification is improved. Moreover, in the foregoing verificationprocess, only through the joint interaction and mutual restriction amongthe application, the target base station, the operator server, and theback-end server, the to-be-verified user can be checked, so as toimprove data security of the entire verification process.

Further, based on the foregoing method shown in FIG. 5, an embodiment ofthe present specification further provides a user verification devicefor signing a fast payment with a bank card. FIG. 8 is a schematicstructural diagram of a user verification device for signing a fastpayment with a bank card, according to an embodiment of the presentspecification. The device is configured to execute the foregoing userverification method based on signing the fast payment of the bank cardin FIG. 5.

As shown in FIG. 8, the user verification device based on signing thefast payment of the bank card may vary a lot due to differentconfigurations or different performance, and may include one or more ofthe processors 801 and a memory 802, and the memory 802 may store one ormore application programs or data. The memory 802 may be a transientstorage or a persistent storage. The application program stored in thememory 802 may include one or more modules (not shown in the figure),and each module may include a series of computer-executable instructionsin the user verification device based on signing the fast payment of thebank card. Furthermore, the processor 801 may be configured tocommunicate with the memory 802, and execute the series ofcomputer-executable instructions in the memory 802 on the userverification device based on signing the fast payment of the bank card.The user verification device based on signing the fast payment of thebank card may further include one or more of the power supply 803, oneor more of the wired or wireless network interface 804, one or more ofthe input/output interface 805, one or more of the keyboard 806, and thelike.

In a specific embodiment, the user verification device based on signingthe fast payment of the bank card includes a memory, and one or moreprograms. The one or more programs are stored in the memory and mayinclude one or more modules, and each module may include a series ofcomputer-executable instructions in a user verification device. The oneor more programs are configured to be executed by one or moreprocessors, and include the computer-executable instructions used forperforming the following operations:

receiving an identification code of an application and a stored mobilephone number that are sent by the application;

receiving a verification request packet sent by the application, atarget base station, and an operator server, wherein the verificationrequest packet is generated according to the identification code of theapplication and basic information of the stored mobile phone number;

verifying a to-be-verified user according to the identification code ofthe application and the stored mobile phone number that are sent by theapplication and the verification request packet; and

sending a verification notification to the application.

Further, when the computer-executable instructions are executed, theverifying a to-be-verified user according to the identification code ofthe application and the stored mobile phone number that are sent by theapplication and the verification request packet includes:

parsing the verification request packet, to obtain basic information ofa stored mobile phone number that corresponds to the verificationrequest packet and an identification code that corresponds to theverification request packet;

matching the stored mobile phone number and the identification code thatcorrespond to the verification request packet with the stored mobilephone number and the identification code of the application that aresent by the application, respectively; and

determining a verification notification according to a matching result.

According to the user verification device based on signing the fastpayment of the bank card provided in the embodiment of the presentspecification, in the foregoing verification process of theto-be-verified user, interactions among the application, the target basestation, the operator server, and the back-end server of the applicationare reduced, the network latency is reduced, and the efficiency of userverification is improved. In addition, in the foregoing verificationprocess, only through the joint interaction and mutual restriction amongthe application, the target base station, the operator server, and theback-end server, the to-be-verified user can be verified, so as toimprove data security of the entire verification process.

Further, an embodiment of the present specification further provides anon-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium is configured to storecomputer-executable instructions. In an embodiment, the non-transitorycomputer-readable storage medium may be a USB flash drive, an opticaldisc, a hard disk, or the like, and the computer-executable instructionsstored in the non-transitory computer-readable storage medium mayimplement the following process when being executed by a processor:

verifying account information of a to-be-verified user based on abanking system;

performing, based on a stored mobile phone number in the accountinformation, a mobile phone number verification on a user terminal inwhich an application is located if the account verification succeeds;

sending an identification code of the application and the stored mobilephone number to a back-end server of the application if the mobile phonenumber verification succeeds, and sending a verification request packetgenerated according to the identification code and basic information ofthe stored mobile phone number to a target base station;

receiving a verification notification for the to-be-verified userreturned by the back-end server according to the identification code ofthe application and the stored mobile phone number that are received andthe verification request packet forwarded by the target base station andan operator server; and

determining, according to the verification notification, whether theverification of the to-be-verified user succeeds.

Further, when the computer-executable instructions stored in thenon-transitory computer-readable storage medium are executed by theprocessor, the performing, based on a stored mobile phone number in theaccount information, a mobile phone number verification on a userterminal in which the application is located includes:

obtaining mobile phone numbers in the user terminal in which theapplication is located; and

determining whether the mobile phone numbers in the user terminalinclude the stored mobile phone number, and determining, according to adetermining result, whether the mobile phone number verification of theuser terminal succeeds.

Further, when the computer-executable instructions stored in thenon-transitory computer-readable storage medium are executed by theprocessor, the sending a verification request packet generated accordingto the identification code and basic information of the stored mobilephone number to a target base station includes:

assembling the basic information of the stored mobile phone number andthe identification code according to a preset format, to generate theverification request packet; and

sending the verification request packet to the target base station.

Further, when the computer-executable instructions stored in thenon-transitory computer-readable storage medium are executed by theprocessor, the sending an identification code of the application and thestored mobile phone number to a back-end server of the application ifthe mobile phone number verification succeeds includes:

displaying an inquiry request about whether to perform the verificationthrough the stored mobile phone number to the to-be-verified user if themobile phone number verification succeeds; and

receiving response information from the to-be-verified user based on theinquiry request, and sending the identification code of the applicationand the stored mobile phone number to the back-end server of theapplication if the response information is confirmation information.

When the computer-executable instructions stored in the non-transitorycomputer-readable storage medium in the embodiment of the presentspecification are executed by the processor, compared with the existingtechnology, only the account information needs to be provided by theto-be-verified user in the entire verification process, to automaticallyverify the to-be-verified user. At the same time, because there is noneed for the to-be-verified user to switch between differentapplications to remember and fill with an SMS verification code, aninteractive operation of the to-be-verified user is greatly simplified,a situation of incorrectly remembering the SMS verification code isavoided, the efficiency and a success rate of the verification areincreased, and the user experience is improved. In addition, in theforegoing verification process of the to-be-verified user, interactionsamong the application, the target base station, the operator server, andthe back-end server of the application are reduced, the network latencyis reduced, and the efficiency of user verification is improved.Moreover, in the foregoing verification process, only through the jointinteraction and mutual restriction among the application, the targetbase station, the operator server, and the back-end server, theto-be-verified user can be verified, so as to improve data security ofthe entire verification process.

Further, an embodiment of the present specification provides anon-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium is configured to storecomputer-executable instructions. In an embodiment, the non-transitorycomputer-readable storage medium may be a USB flash drive, an opticaldisc, a hard disk, or the like, and the computer-executable instructionsstored in the non-transitory computer-readable storage medium mayimplement the following process when being executed by a processor:

receiving an identification code of an application and a stored mobilephone number that are sent by the application;

receiving a verification request packet sent by the application, atarget base station, and an operator server, wherein the verificationrequest packet is generated according to the identification code of theapplication and basic information of the stored mobile phone number;

verifying a to-be-verified user according to the identification code ofthe application and the stored mobile phone number that are sent by theapplication and the verification request packet; and

sending a verification notification to the application.

Further, when the computer-executable instructions stored in thenon-transitory computer-readable storage medium are executed by theprocessor, the verifying a to-be-verified user according to theidentification code of the application and the stored mobile phonenumber that are sent by the application and the verification requestpacket includes:

parsing the verification request packet, to obtain basic information ofa stored mobile phone number that corresponds to the verificationrequest packet and an identification code that corresponds to theverification request packet;

matching the stored mobile phone number and the identification code thatcorrespond to the verification request packet with the stored mobilephone number and the identification code of the application storedmobile phone that are sent by the application, respectively; and

determining a verification notification according to a matching result.

When the computer-executable instructions stored in the non-transitorycomputer-readable storage medium in the embodiment of the presentspecification are executed by the processor, in the foregoingverification process of the to-be-verified user, interactions among theapplication, the target base station, the operator server, and theback-end server of the application are reduced, the network latency isreduced, and the efficiency of user check is improved. In addition, inthe foregoing verification process, only through the joint interactionand mutual restriction among the application, the target base station,the operator server, and the back-end server, the to-be-verified usercan be verified, so as to improve data security of the entireverification process.

In the 1990s, improvements of a technology can be clearly distinguishedbetween hardware improvements (for example, improvements to a circuitstructure such as a diode, a transistor, a switch, etc.) and softwareimprovements (improvements to a method procedure). However, with thedevelopment of technology, improvements of many method procedures can beconsidered as direct improvements of hardware circuit structures. Almostall designers program an improved method procedure to a hardwarecircuit, to obtain a corresponding hardware circuit structure.Therefore, it does not mean that the improvement of a method procedurecannot be implemented by using modules of a hardware entity. Forexample, a programmable logic device (PLD) such as a field programmablegate array (FPGA) is a type of integrated circuit whose logic functionis determined by a user by programming the device. The designers programa digital system to “integrate” the digital system into a single PLDwithout requiring a chip manufacturer to design and manufacture adedicated integrated circuit chip. In addition, instead of making anintegrated circuit chip manually, the programming is mostly implementedby using “logic compiler” software, which is similar to the softwarecompiler used to write programs. Original codes before compiling arealso written in a specific programming language, which is referred to asHardware Description Language (HDL). There are many types of HDLs, suchas Advanced Boolean Expression Language (ABEL), Altera HardwareDescription Language (AHDL), Confluence, Cornell University ProgrammingLanguage (CUPL), HDCal, Java Hardware Description Language (JHDL), Lava,Lola, MyHDL, PALASM, Ruby Hardware Description Language (RHDL), etc.Currently, Very-High-Speed Integrated Circuit Hardware DescriptionLanguage (VHDL) and Verilog are most commonly used. A person skilled inthe art should also understand that as long as a method procedure islogically programmed by using the foregoing hardware descriptionlanguages and then programmed into an integrated circuit, a hardwarecircuit that implements the logical method procedure can be easilyobtained.

The controller can be implemented in any suitable manner, for example,the controller can be in a form of, for example, a microprocessor orprocessor and a computer-readable medium storing computer-readableprogram code (for example, software or firmware) executable by theprocessor, a logic gate, a switch, an application-specific integratedcircuit (ASIC), a programmable logic controller, or an embeddedmicrocontroller. Examples of the controller include, but are not limitedto, the following microcontrollers: ARC 625D, Atmel AT91SAM, MicrochipPIC18F26K20, and Silicone Labs C8051F320. The memory controller can alsobe implemented as a part of the memory control logic. A person skilledin the art will also appreciate that, in addition to implementing thecontroller in the form of pure computer-readable program code, it isalso possible to implement the controller in the form of a logic gate, aswitch, an application-specific integrated circuit, a programmable logiccontroller, an embedded microcontroller, or other forms to achieve thesame functions. Such a controller can thus be considered as a hardwarecomponent, and apparatuses included in the hardware component forimplementing various functions can also be considered as structures ofthe hardware component. Alternatively, apparatuses configured toimplement various functions can be considered as software modulesimplementing the method as well as the structures inside the hardwarecomponent.

The system, the apparatus, the module, or the unit described in theforegoing embodiments can be specifically implemented by a computer chipor an entity, or can be implemented by a product having certainfunctions. A typical implementation device is a computer. Specifically,the computer can be, for example, a personal computer, a laptopcomputer, a cellular phone, a camera phone, a smartphone, a personaldigital assistant, a media player, a navigation device, an email device,a game console, a tablet computer, a wearable device, or a combinationof any of these devices.

For ease of description, the foregoing apparatus is described usingvarious units that perform various functions. Certainly, duringimplementation of one or more embodiments of the present specification,the functions of each unit may be implemented in a same piece of or aplurality of pieces of software and/or hardware.

A person skilled in the art should understand that the one or moreembodiments of the present specification may be provided as a method, asystem, or a computer program product. Therefore, the one or moreembodiments of the present specification may use embodiments in a formof hardware only, software only, or a combination of software andhardware. Moreover, the one or more embodiments of the presentspecification may use a form of a computer program product that isimplemented on one or more computer-readable storage media (includingbut not limited to a disk memory, a CD-ROM, an optical memory, or thelike) that includes computer-readable program codes.

The one or more embodiments of the present specification are describedwith reference to the flowcharts and/or block diagrams of the method,the device (system), and the computer program product according to theembodiments of the present specification. It should be understood thatcomputer program instructions may be used to implement each processand/or each block in the flowcharts and/or block diagrams, or acombination of a process and/or a block in the flowcharts and/or theblock diagrams. These computer program instructions may be provided to ageneral-purpose computer, a special-purpose computer, an embeddedprocessor, or a processor of another programmable data processing deviceto generate a machine, so that an apparatus configured to implementfunctions specified in one or more procedures in the flowcharts and/orone or more blocks in the block diagrams is generated by usinginstructions executed by the computer or the processor of anotherprogrammable data processing device.

These computer program instructions may also be stored in a computerreadable memory that can guide a computer or another programmable dataprocessing device to operate in a specific manner, so that theinstructions stored in the computer readable memory generate a productincluding an instruction apparatus, wherein the instruction apparatusimplements functions specified in one or more procedures in theflowcharts and/or one or more blocks in the block diagrams.

These computer program instructions may also be loaded into a computeror another programmable data processing device, so that a series ofoperation steps are performed on the computer or another programmabledata processing device to generate procedures implemented by a computer,and instructions executed on the computer or another programmable dataprocessing device provide steps for implementing functions specified inone or more procedures in the flowcharts and/or one or more blocks inthe block diagrams.

In a typical configuration, a computing device includes one or moreprocessors (CPU), an input/output interface, a network interface, and amemory.

The memory may include the following forms of computer readable media: anon-persistent memory, a random access memory (RAM), and/or anon-volatile memory, for example, a read-only memory (ROM) or a flashmemory (flash RAM). The memory is an example of a computer readablemedium.

The computer readable media may implement information storage using anymethod or technology, and may include persistent or non-persistent, andmobile or non-mobile media. The information may be a computer readableinstruction, a data structure, a program module, or other data. Examplesof computer storage media include, but not limited to, a phase changememory (PRAM), a static random access memory (SRAM), a dynamic randomaccess memory (DRAM), other type of random access memory (RAM), aread-only memory (ROM), an electrically erasable programmable read-onlymemory (EEPROM), a flash memory or other memory technology, a compactdisc read-only memory (CD-ROM), a digital versatile disc (DVD) or otheroptical storage, a cassette magnetic tape, tape and disk storage orother magnetic storage device or any other non-transmission media thatmay be configured to store information that a computing device canaccess. Based on the definition in the present context, thecomputer-readable medium does not include transitory computer readablemedia (transitory media), such as a modulated data signal and a carrier.

It should also be noted that the terms “include”, “comprise”, and anyother variants cover the non-exclusive inclusion. Thereby, the process,method, article, or device which include a series of elements not onlyinclude those elements, but also include other elements which are notexplicitly listed, or include the inherent elements of the process,method, article and device. An element preceded by “includes a . . . ”does not, without more constraints, preclude the existence of additionalidentical elements in the process, method, article, or apparatus thatincludes the element.

The one or more embodiments of the present specification can bedescribed in the general context of computer-executable instructionsexecuted by a computer, for example, a program module. Generally, theprogram module includes a routine, a program, an object, a component, adata structure, and the like for executing a particular task orimplementing a particular abstract data type. This application may bepracticed in distributed computing environments in which tasks areperformed by remote processing devices that are connected through acommunications network. In a distributed calculating environment,program modules may be located in both local and remote computer storagemedia including storage devices.

In the present specification, the embodiments are described in aprogressive manner Same or similar part of the embodiments may bereferred to each other. Each embodiment focuses on a difference fromother embodiments. Especially, the system embodiment is basicallysimilar to the method embodiments, and therefore it is describedbriefly. Relevant parts in the system embodiment may be referred to thedescription of the part of the method embodiments.

The foregoing descriptions are merely one or more embodiments of thepresent specification, and do not limit the present specification. For aperson skilled in the art, various modifications and variations can bemade to the one or more embodiments of the present specification. Anymodification, equivalent replacement, or improvement made withoutdeparting from the spirit and principle of one or more embodiments ofthe present specification shall fall within the scope of the claims ofone or more embodiments of the present specification.

What is claimed is:
 1. A verification method comprising: performing, byan application, an account verification on account information of ato-be-verified user; performing, by the application, based on a storedmobile phone number in the account information, a mobile phone numberverification on a user terminal in which the application is located ifthe account verification succeeds; sending, by the application, anidentification code of the application and the stored mobile phonenumber to a back-end server of the application if the mobile phonenumber verification succeeds, and sending a verification request packetgenerated according to the identification code and basic information ofthe stored mobile phone number to a target base station, wherein: thetarget base station is configured to verify validity of the storedmobile phone number according to the verification request packet, andsend the verification request packet to an operator server if thevalidity of the stored mobile phone number is verified; the operatorserver is configured to verify validity of the target base station, andforward the received verification request packet to the back-end serverif the validity of the target base station is verified; and the back-endserver is configured to perform a verification on the to-be-verifieduser to generate a verification notification according to theverification request packet sent by the operator server, and theidentification code and the stored mobile phone number sent by theapplication; receiving, by the application, the verificationnotification returned by the back-end server, and determining, accordingto the verification notification, whether the verification of theto-be-verified user succeeds; and performing, by the application, a fastpayment signing process to generate a fast payment agreement when theverification of the to-be-verified user succeeds.
 2. The verificationmethod according to claim 1, wherein the performing, by the application,based on a stored mobile phone number in the account information, amobile phone number verification on a user terminal in which theapplication is located comprises: obtaining, by the application, atleast one mobile phone number of the user terminal in which theapplication is located; determining, by the application, whether the atleast one mobile phone number of the user terminal comprises the storedmobile phone number; and determining, by the application, in response todetermining that the at least one mobile phone number of the userterminal comprises the stored mobile phone number, whether the mobilephone number verification of the user terminal succeeds.
 3. Theverification method according to claim 1, wherein the sending averification request packet generated according to the identificationcode and basic information of the stored mobile phone number to a targetbase station comprises: assembling, by the application, the basicinformation of the stored mobile phone number and the identificationcode according to a preset format to generate the verification requestpacket; and sending, by the application, the verification request packetto the target base station.
 4. The verification method according toclaim 1, wherein the target base station is configured to verifyvalidity of the stored mobile phone number according to the verificationrequest packet by: parsing, by the target base station, the verificationrequest packet to obtain the basic information of the stored mobilephone number; obtaining, by the target base station, verificationinformation of each candidate mobile phone number from the operatorserver, wherein the verification information of each candidate mobilephone number comprises basic information and state information;matching, by the target base station, the stored mobile phone numberwith each candidate mobile phone number, and determining a candidatemobile phone number matching the stored mobile phone number as ato-be-compared mobile phone number; matching, by the target basestation, the basic information of the stored mobile phone number withbasic information of the to-be-compared mobile phone number, anddetermining state information of the to-be-compared mobile phone numberas state information of the stored mobile phone number if the basicinformation of the stored mobile phone number matches the basicinformation of the to-be-compared mobile phone number; determining, bythe target base station, according to the state information of thestored mobile phone number, whether the stored mobile phone number is ina preset state; and determining, in response to determining that thestored mobile phone number is in the preset state, whether the validityof the stored mobile phone number is verified.
 5. The verificationmethod according to claim 1, wherein the operator server is configuredto verify validity of the target base station by: obtaining, by theoperator server, verification information of the target base station;and determining, by the operator server, according to the verificationinformation of the target base station and verification information ofeach candidate base station in the operator server, whether the validityof the target base station is verified.
 6. The verification methodaccording to claim 1, wherein the sending, by the application, anidentification code of the application and the stored mobile phonenumber to a back-end server of the application if the mobile phonenumber verification succeeds comprises: displaying, by the application,an inquiry request about whether to perform the verification through thestored mobile phone number to the to-be-verified user if the mobilephone number verification succeeds; and receiving, by the application,response information of the to-be-verified user based on the inquiryrequest, and sending the identification code of the application and thestored mobile phone number to the back-end server of the application ifthe response information includes a confirmation message.
 7. Theverification method according to claim 1, wherein the back-end server isconfigured to perform the verification on the to-be-verified user togenerate the verification notification according to the verificationrequest packet sent by the operator server and the identification codeand the stored mobile phone number sent by the application by: parsing,by the back-end server, the verification request packet to obtain basicinformation of a stored mobile phone number corresponding to theverification request packet and an identification code corresponding tothe verification request packet; matching, by the back-end server, thestored mobile phone number and the identification code corresponding tothe verification request packet with the stored mobile phone number andthe identification code sent by the application to generate a matchingresult; and determining, by the back-end server, the verificationnotification according to the matching result.
 8. A verification devicecomprising: at least one processor; and a memory storingcomputer-executable instructions executable by the at least oneprocessor to cause the at least one processor to perform operationsincluding: performing, by an application, an account verification onaccount information of a to-be-verified user; performing, by theapplication, based on a stored mobile phone number in the accountinformation, a mobile phone number verification on a user terminal inwhich the application is located if the account verification succeeds;sending, by the application, an identification code of the applicationand the stored mobile phone number to a back-end server of theapplication if the mobile phone number verification succeeds, andsending a verification request packet generated according to theidentification code and basic information of the stored mobile phonenumber to a target base station, wherein: the target base station isconfigured to verify validity of the stored mobile phone numberaccording to the verification request packet, and send the verificationrequest packet to an operator server if the validity of the storedmobile phone number is verified, wherein the at least one processorcomprises the back-end server and the operator server; the operatorserver is configured to verify validity of the target base station, andforward the received verification request packet to the back-end serverif the validity of the target base station is verified; and the back-endserver is configured to perform a verification on the to-be-verifieduser to generate a verification notification according to theverification request packet sent by the operator server, and theidentification code and the stored mobile phone number sent by theapplication; receiving, by the application, the verificationnotification returned by the back-end server, and determining, accordingto the verification notification, whether the verification of theto-be-verified user succeeds; and performing, by the application, a fastpayment signing process to generate a fast payment agreement when theverification of the to-be-verified user succeeds.
 9. The verificationdevice according to claim 8, wherein the operations further comprise:obtaining, by the application, at least one mobile phone number of theuser terminal in which the application is located; determining, by theapplication, whether the at least one mobile phone number of the userterminal comprises the stored mobile phone number; and determining, bythe application, in response to determining that the at least one mobilephone number of the user terminal comprises the stored mobile phonenumber, whether the mobile phone number verification of the userterminal succeeds.
 10. The verification device according to claim 8,wherein the operations further comprise: if the mobile phone numberverification succeeds, assembling, by the application, the basicinformation of the stored mobile phone number and the identificationcode according to a preset format to generate the verification requestpacket; and sending, by the application, the verification request packetto the target base station.
 11. The verification device according toclaim 8, wherein the operations further comprise: if the validity of thestored mobile phone number is verified, parsing, by the target basestation, the verification request packet to obtain the basic informationof the stored mobile phone number; obtaining, by the target basestation, verification information of each candidate mobile phone numberfrom the operator server, wherein the verification information of eachcandidate mobile phone number comprises basic information and stateinformation; matching, by the target base station, the stored mobilephone number with each candidate mobile phone number, and determining acandidate mobile phone number matching the stored mobile phone number asa to-be-compared mobile phone number; matching, by the target basestation, the basic information of the stored mobile phone number withbasic information of the to-be-compared mobile phone number, anddetermining state information of the to-be-compared mobile phone numberas state information of the stored mobile phone number if the basicinformation of the stored mobile phone number matches the basicinformation of the to-be-compared mobile phone number; determining, bythe target base station, according to the state information of thestored mobile phone number, whether the stored mobile phone number is ina preset state; and determining, in response to determining that thestored mobile phone number is in the preset state, whether the validityof the stored mobile phone number is verified.
 12. The verificationdevice according to claim 8, wherein the operations further comprise: ifthe validity of the target base station is verified, obtaining, by theoperator server, verification information of the target base station;and determining, by the operator server, according to the verificationinformation of the target base station and verification information ofeach candidate base station in the operator server, whether the validityof the target base station is verified.
 13. The verification deviceaccording to claim 8, wherein the operations further comprise: if themobile phone number verification succeeds, displaying, by theapplication, an inquiry request about whether to perform theverification through the stored mobile phone number to theto-be-verified user if the mobile phone number verification succeeds;and receiving, by the application, response information of theto-be-verified user based on the inquiry request, and sending theidentification code of the application and the stored mobile phonenumber to the back-end server of the application if the responseinformation includes a confirmation message.
 14. The verification deviceaccording to claim 8, wherein the operations further comprise: if themobile phone number verification succeeds, parsing, by the back-endserver, the verification request packet to obtain basic information of astored mobile phone number corresponding to the verification requestpacket and an identification code corresponding to the verificationrequest packet; matching, by the back-end server, the stored mobilephone number and the identification code corresponding to theverification request packet with the stored mobile phone number and theidentification code sent by the application to generate a matchingresult; and determining, by the back-end server, the verificationnotification according to the matching result.
 15. A non-transitorycomputer-readable storage medium storing computer instructionsexecutable by at least one processor to cause the at least one processorto perform operations comprising: performing, by an application, anaccount verification on account information of a to-be-verified user;performing, by the application, based on a stored mobile phone number inthe account information, a mobile phone number verification on a userterminal in which the application is located if the account verificationsucceeds; sending, by the application, an identification code of theapplication and the stored mobile phone number to a back-end server ofthe application if the mobile phone number verification succeeds, andsending a verification request packet generated according to theidentification code and basic information of the stored mobile phonenumber to a target base station, wherein: the target base station isconfigured to verify validity of the stored mobile phone numberaccording to the verification request packet, and send the verificationrequest packet to an operator server if the validity of the storedmobile phone number is verified, wherein the at least one processorcomprises the back-end server and the operator server; the operatorserver is configured to verify validity of the target base station, andforward the received verification request packet to the back-end serverif the validity of the target base station is verified; and the back-endserver is configured to perform a verification on the to-be-verifieduser to generate a verification notification according to theverification request packet sent by the operator server, and theidentification code and the stored mobile phone number sent by theapplication; receiving, by the application, the verificationnotification returned by the back-end server, and determining, accordingto the verification notification, whether the verification of theto-be-verified user succeeds; and performing, by the application, a fastpayment signing process to generate a fast payment agreement when theverification of the to-be-verified user succeeds.
 16. The non-transitorycomputer-readable storage medium according to claim 15, wherein theoperations further comprise: obtaining, by the application, at least onemobile phone number of the user terminal in which the application islocated; determining, by the application, whether the at least onemobile phone number of the user terminal comprises the stored mobilephone number; and determining, by the application, in response todetermining that the at least one mobile phone number of the userterminal comprises the stored mobile phone number, whether the mobilephone number verification of the user terminal succeeds.
 17. Thenon-transitory computer-readable storage medium according to claim 15,wherein the operations further comprise: if the mobile phone numberverification succeeds, assembling, by the application, the basicinformation of the stored mobile phone number and the identificationcode according to a preset format to generate the verification requestpacket; and sending, by the application, the verification request packetto the target base station.
 18. The non-transitory computer-readablestorage medium according to claim 15, wherein the operations furthercomprise: if the validity of the stored mobile phone number is verified,parsing, by the target base station, the verification request packet toobtain the basic information of the stored mobile phone number;obtaining, by the target base station, verification information of eachcandidate mobile phone number from the operator server, wherein theverification information of each candidate mobile phone number comprisesbasic information and state information; matching, by the target basestation, the stored mobile phone number with each candidate mobile phonenumber, and determining a candidate mobile phone number matching thestored mobile phone number as a to-be-compared mobile phone number;matching, by the target base station, the basic information of thestored mobile phone number with basic information of the to-be-comparedmobile phone number, and determining state information of theto-be-compared mobile phone number as state information of the storedmobile phone number if the basic information of the stored mobile phonenumber matches the basic information of the to-be-compared mobile phonenumber; determining, by the target base station, according to the stateinformation of the stored mobile phone number, whether the stored mobilephone number is in a preset state; and determining, in response todetermining that the stored mobile phone number is in the preset state,whether the validity of the stored mobile phone number is verified. 19.The non-transitory computer-readable storage medium according to claim15, wherein the operations further comprise: if the validity of thetarget base station is verified, obtaining, by the operator server,verification information of the target base station; and determining, bythe operator server, according to the verification information of thetarget base station and verification information of each candidate basestation in the operator server, whether the validity of the target basestation is verified.
 20. The non-transitory computer-readable storagemedium according to claim 15, wherein the operations further comprise:if the mobile phone number verification succeeds, parsing, by theback-end server, the verification request packet to obtain basicinformation of a stored mobile phone number corresponding to theverification request packet and an identification code corresponding tothe verification request packet; matching, by the back-end server, thestored mobile phone number and the identification code corresponding tothe verification request packet with the stored mobile phone number andthe identification code sent by the application to generate a matchingresult; and determining, by the back-end server, the verificationnotification according to the matching result.